Microsoft Learning Components (MLC) is a collection of software components that a Windows desktop- or server-based application can use to provide support for playback of e-learning content. MLC supports the industry-standard Sharable Content Object Reference Model (SCORM) e-learning package format as well as the Microsoft Class Server LRM and IMS+ formats.
One application built on MLC is SharePoint Learning Kit (SLK). SLK is a SharePoint 3.0 solution which implements an e-learning runtime for SCORM and Class Server content stored in SharPoint document libraries.
The SLK/MLC software development kit (SDK) contains programming resources required to develop both SLK extensions and MLC applications. For MLC development, the SLK/MLC SDK includes:
This page begins the MLC overview documentation. If you'd like to read this documentation in order, look for the "Next Topic" link at the bottom of this and subsequent pages.
Microsoft Learning Components includes several .NET assemblies, described below, as well as ASP.NET application code (the session frameset) which you may redistribute with your application provided that you comply with the terms of the SharePoint Learning Kit license (see License.txt in the SLK/MLC SDK). Your application will typically install these assemblies either in the global assembly cache or in your application's "bin" directory. The session frameset, on the other hand, is intended as "reusable code": you'll likely modify at least portions of it to suit the needs of your application.
Since applications that leverage Microsoft Learning Components may be web-based, desktop, or console applications, functionality within MLC has been organized into assemblies with the goal of maximizing deployment flexibility. For example, if your application only needs to validate an e-learning package, it need not include Microsoft.LearningComponents.Storage.dll (which has a dependency on SQL Server) or Microsoft.LearningComponents.SharePoint.dll (which has a dependency on SharePoint.
The following diagram shows examples of three applications that leverage MLC. The first depends only on Microsoft.LearningComponents.dll (like the example above), which provides basic support for reading and validating e-learning packages. The second application also leverages Microsoft.LearningComponents.Storage.dll, which adds the ability to execute e-learning packages, with the results stored in a database. The third application adds a dependency on Microsoft.LearningComponents.SharePoint.dll, which adds support for executing packages stored in SharePoint document libraries. SharePoint Learning Kit is an example of the third type of application.

The following table provides an overview of the three public MLC assemblies plus the session frameset.
| Component | Features/Classes | Minimum Requirements |
| Microsoft.LearningComponents.dll |
|
Windows XP |
| Microsoft.LearningComponents.Storage.dll |
|
Windows XP SQL Server 2005 |
| Microsoft.LearningComponents.SharePoint.dll |
|
Windows XP SQL Server 2005 Windows SharePoint Services 3.0 |
| Session Frameset |
Windows XP |
** Applications may derive from these base classes to create custom implementations that can interoprate with other MLC classes.
Note MLC includes a fourth assembly, Microsoft.LearningComponents.Compression.dll, which is for internal use by MLC and should not be accessed directly by applications.
The following table shows how MLC functionality is divided among the namespaces implemented in its managed-code assemblies. Click on a feature hyperlink (right column) for overview information; click on a namespace hyperlink (left column) for detailed API reference documentation.
| Namespace | Features |
| Microsoft.LearningComponents | |
| Microsoft.LearningComponents.DataModel | |
| Microsoft.LearningComponents.Manifest | |
| Microsoft.LearningComponents.SharePoint | |
| Microsoft.LearningComponents.Storage | |
| Microsoft.LearningComponents.Storage.BaseSchema |
|